5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
- Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-5: The Appx ILF Debugger

Single Step


stepOver.png Single Step [RETURN] - Execute the current line and stop on the next line in the current routine.

This option allows you to 'step through' the routine one statement at a time by executing the current line (which is highlighted).

The logic of the current statement executes.

The data values change to reflect the result of executing the current statement.

The cursor moves to the next logical line in the routine, and it becomes the new current line (and is highlighted).

One important thing to note about Return is that the next statement is the next executable statement, not necessarily the next sequential statement. For example, in the following routine:

        IF       TAR WORK AVAILABLE CREDIT           LT     0
   T    WARNING  Customer Has Exceeded Credit Limit!
        DISPLAY  TAR WORK AVAILABLE CREDIT

If the IF statement in this example encounters a false condition and sets the first true/false status indicator to F, the WARNING statement is not executed. By using Return to single-step, the debugger skips from the IF statement directly to the DISPLAY statement.

Additionally, using Return at a COPY or GOSUB statement takes you to the first executable statement immediately following the COPY or GOSUB statement, allowing you to skip over the statements in the subroutine.

Application Design Manual                                         "Powered by Appx Software"

942

©2006 By APPX Software, Inc. All Rights Reserved